FebruaryThe effective date for all products within the scope of this document for this release is February 9 for the CT environment and February 16 for the Production environment.
| Document/transaction expiration behavior modified |
|---|
|
|
| Summary: Users can now identify the number of days to retain transaction data and documents on a transaction by transaction basis or at an Account level; when the default (7 days) does not meet their needs. |
| Implementation Notes: We have repurposed the <DaysToPersistInLongTermStorage/> element in the SelectAndGenerateRequest and GenerateRequest API methods to support setting a number of days to retain if something other than the default is desired. Note: If interested in this functionality please contact your Professional Services representatives.
|
| Ability to merge closing disclosures with addendum |
|---|
- Type: New Feature
- Reference: PBI 419537
- Compliance Impacts: This new feature is not a compliance or regulatory issue.
- Documentation Impacts: MergeTRIDDocs flag - PDF.
|
Summary: We have implemented a new <MergeTRIDDocs/> element that allows users to merge the following TRID documents through the request file:- ClosingDisclosure
- ClosingDisclosureAddendum
- ClosingDisclosure-SellerOnly
- ClosingDisclosure-SellerOnly-Addendum
|
| Technical Notes: With this enhancement, if the <MergeTRIDDocs/> flag is set to "true" in a Select and Generate or Generate request, the addendums above are merged with the associcated closing disclosure into a single standard PDF file. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance is removed from the response. |
| Implementation Notes: For more information, see MergeTRIDDocs flag - PDF. |
